-
Notifications
You must be signed in to change notification settings - Fork 2
Use Jupyter Book for documentation. #65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: buid-docs-using-pixi
Are you sure you want to change the base?
Conversation
3f731b3 to
cf881f5
Compare
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## buid-docs-using-pixi #65 +/- ##
=====================================================
Coverage 95.57% 95.57%
=====================================================
Files 23 23
Lines 1174 1174
=====================================================
Hits 1122 1122
Misses 52 52 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
|
I much prefer the JB-based version over the Sphinx-based one. Differences:
But no big deal if we went back to #63 |
|
Switching to Jupyterbook is ok and the new page does look better. However, I would keep the API docs in. It's almost zero cost to have it and I do use online API docs sometimes. Does Jupyterbook have a good way of producing an llms.txt? If we touch the docs this would be the right time to add it. |
|
Is it okay to postpone API docs until this one is there? jupyter-book/mystmd#1259 Would much prefer that over using Sphinx for now and then porting. Writing native MyST is so much nicer! |
No description provided.